Hello and welcome. In this video you'll get a glimpse
of a model driven app called fundraiser that was designed
using the app designer. Let's check it out. On the app designer screen. You'll be able to find two tables that
are placed underneath one another. The first one is called donation and
the second one is called fundraiser. Next to each one of these two tables,
you'll find four asset blocks, forms, views, charts and dashboards. Forms to find how users will see and
interact with the data. While views enable you to see a list
view of the rows for each table. Charts, display the data in
a meaningful and visual representation. And dashboards provide you
with an insightful and graphical overview of the data. On the app designer screen. You'll be able to select the play
button in the top right corner, curious to know what happens
when you press this button. After clicking the play button,
a preview of the dashboard will appear. The dashboard will give you
a colorful graphical and insightful view of the data that
you've configured in the app designer, It contains charts, graphs and
more exciting elements. The name says it all. With model driven apps your primary design
goal is to get your Microsoft data verse data, model in order. When all of that is in place,
you can connect power ups and a model driven app will be created for
you from that model. Have you ever been to a restaurant
where you get to pick all your favorite toppings to
build your very own meal. Building a model driven app with
app designer is as simple as that. You get to pick the entities, dashboards,
business process flows, forms and any other components that you want
to make available in your app and then the app will be created for you. But first you need to ask
yourself a few questions. The first question is, what type of data
will your solution be storing and or collecting? And the next question is how
will this data relate or correspond with the other
data you're working with? You might be wondering
why this is important. These questions are important when
designing a model driven app because of how model driven applications function. Remember model driven applications
use a metadata driven architecture. This means a large portion of the model
driven app is based on how your data is modeled. And don't worry you don't need to write
custom code or change the app design. Next you'll be able to view the app
metadata by reviewing the table in Microsoft data verse. On the next screen you'll be able to view
the various pieces of data that can be collected. In this example of the fundraiser table, there are several pieces of data that
are being collected such as name, fundraiser goal owner,
total donations and created on. You can also preview what the data
will look like in the apps play mode. When adding columns into your table in
Microsoft data versus the data type you choose will determine how users enter and
view that in your model driven app. Let's simplify that a bit. The data types that you've selected
in the data verse will determine what the user sees in the app. When you set the data type for
a column to choice, the user will find a drop
down list in the app. If you choose currency, the figures will automatically
have a currency symbol in the app. However, there will be no currency symbol
in the app if the data types selected is decimal. These little changes in your table can
have a profound effect on how your user experience is your app. Let's go back to our fundraiser example,
in this table you can review examples of columns as well as different
types of data that fundraiser have used. It is very important to remember that if
you need to change a column to a different data type, it might not be that simple. You will need to delete that column and
recreate it with the correct data type. But be careful as it will cause you to
lose any data that is associated with that column